Task packaging as container image. #2285
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is an alternative to #1875 (and #1868?) and just simply distributes task in a container. People can use this image in a multi-stage build to directly install the task binary and avoid compilation delay of manually installing task. And also to pin versions. Generally, running task in a container provided by go-task is not itself useful, since: we (royal "we") are not going to trust that image (at all!); we put a lot of effort into our own images; and in any case we need to package additional tools which task itself is then automating. Also, providing docker images for broad distribution is a lot of stuffing around ... Therefore this alternative is provided. |
|
Better to use goreleaser for this project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a dockerfile and workflow for distributing Task in a scratch based image. Images would be pushed to GHCR, which is significantly less a pain in the arse than pushing images to Docker Hub, but you can do that too ... I doubt its worth the effort!
Workflow integration is tedious, the example I have provided should work out-of-the-box.
edit: ... however, the workflow should probably be triggered after all other checks have occured, which is to say ... after the normal release process has completed (and binaries are published).
fixes #1801